Information processing apparatus and method, program, and recording medium

ABSTRACT

An information processing apparatus for reproducing metadata including information on material data, the information processing apparatus includes determining means for determining whether or not the metadata inputted is defined in advance, and reproducing means for reproducing standard item data and non-standard item data included in the metadata when the determining means determines that the metadata is defined in advance, and reproducing only the standard item data included in the metadata when the determining means determines that the metadata is not defined in advance.

BACKGROUND OF THE INVENTION

[0001] The present invention relates to an apparatus and a method forinformation processing, a program, and a recording medium, andparticularly to an apparatus and a method for information processing, aprogram, and a recording medium that make it possible to retrieve andedit image data and the like more easily.

[0002] Recently, use of metadata describing information on data of takenvideo material (the data will hereinafter be described also as materialdata) has been making progress in a field of production of videoproducts such as TV programs, video contents and the like. Metadata isused to retrieve material data and edit the material data.

[0003] For effective use of metadata, compatibility of the metadatabetween a plurality of apparatus used in production of video products isrequired so that the metadata generated by a video signal recordingapparatus such as a video camera, for example, can be used by a videosignal reproducing apparatus such as an editing apparatus or the like.

[0004] Accordingly, standardization of a metadata description format hasbeen under way in order to provide consistency in the description formatand meanings of metadata. For example, MPEG (Moving Picture ExpertsGroup) 7 has standardized a metadata description format by describingmetadata using a highly versatile XML (extensible Markup Language).

[0005] However, even though metadata has been standardized, there isroom left for each manufacturer to originally extend and describemetadata because concepts and objectives vary in practice amongmanufacturers that manufacture and sell video signal recording apparatusand video signal reproducing apparatus.

SUMMARY OF THE INVENTION

[0006] The present invention has been made in view of the above, and itis an object of the present invention to prevent trouble caused bymetadata extended by another manufacturer independently whilemaintaining compatibility of the metadata.

[0007] According to the present invention, there is provided aninformation processing apparatus including: determining means fordetermining whether or not metadata inputted is defined in advance; andreproducing means for reproducing standard item data and non-standarditem data included in the metadata when the determining means determinesthat the metadata is defined in advance, and reproducing only thestandard item data included in the metadata when the determining meansdetermines that the metadata is not defined in advance.

[0008] The metadata can be described using one of XML and BiM, which isa binary format of XML.

[0009] The determining means can determine whether or not the metadatais defined in advance on a basis of whether or not a name spaceidentifier described in the metadata is defined in a schema possessed bythe information processing apparatus.

[0010] The metadata can be real time metadata to be read simultaneouslywith reproduction of material data.

[0011] According to the present invention, there is provided aninformation processing method including: a determining step fordetermining whether or not metadata inputted is defined in advance; anda reproducing step for reproducing standard item data and non-standarditem data included in the metadata when it is determined by processingof the determining step that the metadata is defined in advance, andreproducing only the standard item data included in the metadata when itis determined by the processing of the determining step that themetadata is not defined in advance.

[0012] According to the present invention, there is provided a programfor making a computer execute a process including: a determining stepfor determining whether or not metadata inputted is defined in advance;and a reproducing step for reproducing standard item data andnon-standard item data included in the metadata when it is determined byprocessing of the determining step that the metadata is defined inadvance, and reproducing only the standard item data included in themetadata when it is determined by the processing of the determining stepthat the metadata is not defined in advance.

[0013] According to the present invention, there is provided a programon a recording medium, the program including: a determining step fordetermining whether or not metadata inputted is defined in advance; anda reproducing step for reproducing standard item data and non-standarditem data included in the metadata when it is determined by processingof the determining step that the metadata is defined in advance, andreproducing only the standard item data included in the metadata when itis determined by the processing of the determining step that themetadata is not defined in advance.

[0014] The information processing apparatus and method, and the programaccording to the present invention reproduce standard item data andnon-standard item data included in metadata when it is determined thatthe metadata inputted is defined in advance, and reproduce only thestandard item data included in the metadata when it is determined thatthe metadata is not defined in advance.

[0015] According to the present invention, it is possible to retrieveand edit image data and the like more easily.

[0016] Further, according to the present invention, it is possible toprevent trouble caused by metadata extended by another manufacturerindependently while maintaining compatibility of the metadata.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017]FIG. 1 is a diagram showing an example of configuration of a videoprogram production support system to which the present invention isapplied;

[0018]FIG. 2 is a block diagram showing an example of internalconfiguration of an editing terminal apparatus in FIG. 1;

[0019]FIGS. 3A and 3B are schematic diagrams showing examples ofstructure of data recorded on an optical disk in FIG. 1;

[0020]FIG. 4 is a diagram showing an example of a directory structurefor managing data by a file system;

[0021]FIG. 5 is a diagram showing a more detailed example of thedirectory structure in FIG. 4;

[0022]FIG. 6 is a diagram showing a more detailed example of thedirectory structure in FIG. 4;

[0023]FIG. 7 is a diagram showing an example of standard real timemetadata described by XML before being encoded into a BiM;

[0024]FIG. 8 is a diagram showing an example of non-standard real timemetadata described by XML before being encoded into a BiM;

[0025]FIG. 9 is a flowchart of assistance in explaining processing fordescribing standard real time metadata before being encoded into a BiM;

[0026]FIG. 10 is a flowchart of assistance in explaining processing fordescribing non-standard real time metadata before being encoded into aBiM;

[0027]FIG. 11 is a flowchart of assistance in explaining processing forreading a BiM using an original schema;

[0028]FIG. 12 is a flowchart of assistance in explaining processing forreading non-real time metadata including original items; and

[0029]FIG. 13 is a flowchart of assistance in explaining processing forrerecording/transferring non-real time metadata including originalitems.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0030] A preferred embodiment of the present invention will hereinafterbe described with reference to the drawings.

[0031]FIG. 1 shows an example of configuration of a video programproduction support system to which the present invention is applied.This video program production support system 1 is for example providedin a television broadcasting station that broadcasts a television signalor a company that produces video contents such as a video, a movie orthe like, to produce a video program as a video product such as atelevision program, a movie or the like. The video program productionsupport system 1 allows metadata formed in an electronic file format andadded to the video program, and the like to be used consistently betweena plurality of divisions sharing the production of the video program.The video program production support system 1 is thus intended to enableefficient production of video programs.

[0032] The video program production support system 1 includes: aplanning terminal apparatus 11 for planning a video program; a network12 connected with the planning terminal apparatus 11; a materialcollecting terminal apparatus 13 connected to the network 12, thematerial collecting terminal apparatus 13 including an image pickupdevice 14 and a field PC/PDA (Personal Computer/Personal DigitalAssistant) 15 (hereinafter referred to as a field PC 15); an editingterminal apparatus 16 similarly connected to the network 12; and anoptical disk 17 as a recording medium.

[0033] The planning terminal apparatus 11 for example includes aninformation processing apparatus such as a personal computer or the likeand a peripheral device or the like. The planning terminal apparatus 11is provided in a planning and organizing division or the like forplanning video programs. The planning and organizing division overseesthe entire production of the video programs. The planning and organizingdivision plans and designs a video program to be produced, creates ascenario (outline) for the video program, and instructs other divisionssuch as a material collecting division, an editing division and the liketo be described later on production operations.

[0034] The planning terminal apparatus 11 performs processing such forexample as generation for each video program of constructing tablemetadata in an electronic file format, the metadata including productioninstruction information and the like corresponding to a scenario for thevideo program. The planning terminal apparatus 11 supplies the generatedconstructing table metadata to the material collecting terminalapparatus 13 and the like via the network 12. The planning andorganizing division instructs the material collecting division and thelike on scenes and contents to be collected or taken.

[0035] The material collecting terminal apparatus 13 is a group ofterminal apparatus used by the material collecting division forcollecting material, and includes the image pickup device 14 and thefield PC 15. The material collecting division actually collects materialat a site of production according to production instructions and ascenario from the planning and organizing division, for example. Thematerial collecting division takes a picture of each scene forconstructing a video program and reports shooting conditions.

[0036] The image pickup device 14 includes a video camera such as acamcorder (registered trademark), for example. The image pickup device14 is used to collect material for a news program to be broadcast ortake a sports game or the like, video contents for a movie or the like.The image pickup device 14 is connected to the network 12 to obtainconstructing table metadata from the planning terminal apparatus 11 viathe network 12, for example. Then, the image pickup device 14 displaysthe obtained constructing table metadata on a predetermined display unitor the like to make a camera crew such as a camera operator and the likerecognize contents to be taken. The image pickup device 14 takes eachscene for constructing the video program on the basis of productioninstruction information in the constructing table metadata operated andobtained by the camera crew. Image data and audio data obtained bytaking images are then recorded on a recording medium such as theoptical disk 17.

[0037] The image pickup device 14 can record onto the optical disk 17not only original image data as the image data obtained by taking imagesbut also low resolution image data (hereinafter referred to as lowresolution data), for example. The original image data, which is a largeamount of data of high quality, is used for a finished product of thevideo program. On the other hand, the low resolution data is image datacorresponding to frame pictures with a smaller number of pixels, whichdata is generated by discretely reducing a number of pixels of eachframe from the original image data, for example. The low resolution datamay be further encoded by an MPEG4 system, for example. The lowresolution data, which is lower in picture quality but smaller in dataamount than the original image data, imposes a light load on processingsuch as transmission, reproduction and the like, and is thus used mainlyfor rough edit processing and the like.

[0038] The optical disk 17 on which the image data, the audio data andthe like are recorded by the image pickup device 14 is conveyed to theediting division to be described later, the field PC 15 or the like, forexample, to be used by the editing division, the field PC 15 or thelike. Since the conveyance of the optical disk 17 takes a certain time,the image pickup device 14 may be able to supply the video contents tothe planning terminal apparatus 11, the field PC 15, the editingterminal apparatus 16 or the like via the network 12. In this case, itis desirable that the image pickup device 14 supply the low resolutiondata small in data amount which data corresponds to the image dataobtained by image pickup in order to reduce transfer time (in order toreduce a load on transfer processing).

[0039] Incidentally, the image pickup device 14 may transfer the lowresolution data in any timing; the image pickup device 14 may transferthe low resolution data in parallel with image pickup processing, or theimage pickup device 14 may transfer the low resolution data en blocafter an end of image pickup processing.

[0040] Thus, transferring the low resolution data prior to theconveyance of the optical disk 17 enables the editing division toperform editing operation in a relatively early stage (in parallel withimage pickup processing, for example) even when the conveyed opticaldisk 17 has not arrived. It is therefore possible to enhance efficiencyof production of video programs. Incidentally, when the low resolutiondata is transmitted via the network 12 as described above, the imagepickup device 14 may record only the original image data and the audiodata onto the optical disk 17, for example (the image pickup device 14does not need to record the low resolution data onto the optical disk17).

[0041] It is to be noted that the recording medium on which videocontents and the like are recorded by the image pickup device 14 is notlimited to the above-described example of the optical disk 17, and maybe any recording medium. For example, the recording medium may be amagnetic disk including a flexible disk, a magnetic tape used in DV(Digital Video) or VHS (Video Home System), a semiconductor memoryincluding a flash memory, or the like.

[0042] The field PC 15 for example includes a portable informationprocessing apparatus such as a notebook personal computer, a PDA or thelike and a peripheral device and the like. The field PC 15 is connectedto the image pickup device 14 by various wire or radio lines or the likeso that the field PC 15 can share for example constructing tablemetadata, video contents and the like with the image pickup device 14.

[0043] The field PC 15 for example obtains the constructing tablemetadata from the planning terminal apparatus 11 via the network 12, orobtains the constructing table metadata from the image pickup device 14.The field PC 15 displays the obtained constructing table metadata on apredetermined display unit to make a person in charge from the materialcollecting division recognize contents to be collected or taken.

[0044] Further, the field PC 15 generates shooting conditioninformation, which is information on material-collecting and shootingconditions, on the basis of input of the person in charge from thematerial collecting division as a user, and adds the generated shootingcondition information in an appropriate section within the constructingtable metadata. This shooting condition information is text data or thelike entered from various viewpoints for each take or at eachmaterial-collecting site, for example, and is useful at a time of editprocessing in a later stage. The field PC 15 thus edits the constructingtable metadata by writing the shooting condition information. The fieldPC 15 also supplies the shooting condition information as metadata tothe image pickup device 14 to add the shooting condition information tothe image data and the audio data obtained in the image pickup device14.

[0045] The editing terminal apparatus 16 for example includes aninformation processing apparatus such as a personal computer or the likeand a peripheral device. The editing terminal apparatus 16 is providedin the editing division for editing video contents. The editing divisionedits the image data and the audio data obtained by the image pickupdevice 14 on the basis of the production instructions and the scenariofrom the planning and organizing division, the constructing tablemetadata reflecting conditions in material collection by the materialcollecting division, and the like, and thereby completes the videoprogram.

[0046] The editing terminal apparatus 16 obtains the updatedconstructing table metadata and the low resolution data from the imagepickup device 14 via the network 12, for example. In addition, theediting terminal apparatus 16 reproduces the original image data and theaudio data from the optical disk 17 on which the image data and theaudio data are recorded by the image pickup device 14. Further, theediting terminal apparatus 16 can obtain the production instructionsdirectly from the planning terminal apparatus 11 via the network 12.

[0047] The editing terminal apparatus 16 suitably reproduces anddisplays the obtained video contents data on the basis of theconstructing table metadata obtained as described above. For example,the editing terminal apparatus 16 continuously displays the lowresolution data operated by the user and obtained via the network 12, orthe original image data and the audio data recorded on the optical disk17 in an order according to the scenario, or displays only image data ofa desired clip. Incidentally, when reproducing the original image datarecorded on the optical disk 17, the editing terminal apparatus 16 usesa disk device or the like as a recording and reproducing device forreading data recorded on the optical disk 17 and writing data to theoptical disk 17, for example.

[0048] The editing terminal apparatus 0.16 not only reproduces anddisplays necessary image data and the like in a suitable order on thebasis of the constructing table metadata, but also performs processingfor editing the image data and the like obtained by collectingmaterials, for example. This edit processing includes rough editprocessing and main edit processing.

[0049] Rough edit processing is simple edit processing on image data andaudio data. For example, in rough edit processing, when the editingterminal apparatus 16 obtains a plurality of pieces of data (hereinafterreferred to as clip data) on video contents including image data, audiodata and the like corresponding to a clip as a unit representing oneimage pickup process, for example, the editing terminal apparatus 16selects clip data to be used in a main edit from these pieces of clipdata. The editing terminal apparatus 16 further selects a necessaryvideo portion from the selected clip data (logging), and sets an editstart position (In point) and an edit end position (Out point)corresponding to the selected video portion by using for example a timecode or the like. The editing terminal apparatus 16 thereby extracts thecorresponding portion from the above-described clip data (ingesting).

[0050] Incidentally, the clip is a unit that not only represents oneimage pickup process but also indicates a time from a start of imagepickup in the image pickup process to an end of the image pickup, alength of various data obtained by the image pickup process, and a dataamount of the various data obtained by the image pickup process.Further, the clip can represent an aggregate itself of the various data.

[0051] Main edit processing connects together pieces of clip data afterbeing subjected to rough edit processing, performs final picture qualityadjustment and the like on the image data, and thus generates completedpackage data as data for broadcasting in a program or the like.

[0052] Incidentally, each of the planning terminal apparatus 11, theimage pickup device 14, the field PC 15, the editing terminal apparatus16 and the like described above may be formed by a plurality ofapparatus. For example, one editing terminal apparatus 16 may obtainimage data and the like obtained in a plurality of image pickup devices14 via the optical disk 17 or the network 12 to perform edit processingon the data, or a plurality of editing terminal apparatus 16 may editdata supplied from one image pickup device 14.

[0053] While each of the planning terminal apparatus 11, the imagepickup device 14, the field PC 15, the editing terminal apparatus 16 andthe like described above is formed as a separate unit, the presentinvention is not limited to this, and a part or all of functions of theapparatus may be integrated with each other.

[0054] In addition, for example a center server (not shown) connected tothe network 12 may be provided in the video program production supportsystem 1 separately from the planning terminal apparatus 11, the imagepickup device 14, the field PC 15, and the editing terminal apparatus 16described above, so that a client/server system may be formed with theplanning terminal apparatus 11, the image pickup device 14, the field PC15, the editing terminal apparatus 16 and the like as clients.

[0055]FIG. 2 shows a detailed example of configuration of the editingterminal apparatus 16 in FIG. 1. A CPU (Central Processing Unit) 51 inthe editing terminal apparatus 16 performs various processing accordingto a program stored in a ROM (Read Only Memory) 52. A RAM (Random AccessMemory) 53 stores data, a program and the like necessary for the CPU 51to perform various processing, as required.

[0056] A clip data editing unit 54 controls an output unit 62 to displaya GUI (Graphical User Interface) or the like on a display or the like.The clip data editing unit 54 performs edit processing on the imagedata, the audio data, the low resolution data, the metadata or the likerecorded on the optical disk 17 loaded in a drive 65, or the lowresolution data or the like obtained via a communicating unit 64 on thebasis of operating input from the user which input is received by aninput unit 61. The clip data editing unit 54 generates information onedit contents, information on data after the edit, and the like, andthen supplies the information to an edit list editing unit 55.Incidentally, the clip data editing unit 54 performs nondestructive editprocessing without updating the various data to be edited.

[0057] The edit list editing unit 55 generates an edit list asinformation on an edit result on the basis of the various informationgenerated in association with the edit processing performed in the clipdata editing unit 54, and then stores the edit list in a storage unit63. At this time, as later described, the edit list editing unit 55generates edit list clip metadata as clip metadata for the edit list onthe basis of clip metadata of a clip being edited, of which metadatareal time performance is not required. For example, on the basis of aconversion table included in clip metadata of a clip being edited, theedit list editing unit 55 generates a conversion table of adiscontinuity point of an LTC (Linear Time Code) corresponding to imagedata and the like of the clip after the edit and a frame number thereof,and then records the conversion table as edit list clip metadata.

[0058] The CPU 51, the ROM 52, the RAM 53, the clip data editing unit54, and the edit list editing unit 55 are interconnected via a bus 56.The bus 56 is also connected with an input/output interface 60.

[0059] The input/output interface 60 is connected with the input unit 61including a keyboard and a mouse for outputting a signal inputted to theinput unit 61 to the CPU 51. The input/output interface 60 is alsoconnected with the output unit 62 including a display, a speaker and thelike.

[0060] Further, the input/output interface 60 is connected with thestorage unit 63 including a hard disk, an EEPROM (ElectronicallyErasable and Programmable Read Only Memory) and the like, as well as thecommunicating unit 64 for communicating data with another apparatus viathe network 12 or the like. The drive 65 is used to read and write datafrom and to a removable medium 71 including a recording medium such as amagnetic disk, an optical disk, a magneto-optical disk, a semiconductormemory or the like.

[0061] Description will next be made of the optical disk 17 and anexample of structure of data recorded on the optical disk 17 used inedit processing by such an editing terminal apparatus 16.

[0062] As the optical disk 17, various optical disks and the like can beused, such for example as DVD-RAM (Digital Versatile Disc-Random AccessMemory), DVD-R (DVD-Recordable), DVD-RW (DVD-ReWritable), DVD+R(DVD+Recordable), DVD+RW (DVD+ReWritable), CD-R (CompactDisc-Recordable), CD-RW (CD-ReWritable), or MD (Mini Disc) (registeredtrademark).

[0063] As described above, the image pickup device 14 records aplurality of pieces of clip data including image data, audio data andthe like on the optical disk 17 as a recording medium as shown in FIG.3A, for example.

[0064] In FIG. 3A, annual ring data 80 including audio annual ring data81, video annual ring data 82, low resolution annual ring data 83, andframe meta annual ring data 84 corresponding to a predetermined timeunit (for example two seconds) obtained by the image pickup device 14 isrecorded continuously for one clip on the optical disk 17. Clip metadata91 corresponding to the clip is recorded following last annual ring data80. Further, annual ring data and clip metadata corresponding to anotherclip and the like are subsequently recorded.

[0065] The audio annual ring data 81 and the video annual ring data 82have the same reproduction time and correspond to each other. That is,the audio annual ring data 81 is audio data corresponding to movingpictures obtained by reproducing the video annual ring data 82. The lowresolution annual ring data 83 corresponds to the video annual ring data82, and has the same reproduction time as the video annual ring data 82.That is, the low resolution annual ring data 83 corresponds to movingpictures of a small picture size resulting from reduction of picturesize of the moving pictures obtained by reproducing the video annualring data 82. The frame meta annual ring data 84 includes metadata(hereinafter referred to as frame metadata) added to each frame (imagedata for one screen) of the moving pictures corresponding to the videoannual ring data 82. That is, the frame meta annual ring data includes aplurality of pieces of frame metadata corresponding to all frames of thevideo annual ring data 82.

[0066] Incidentally, frame metadata is data corresponding to a frame towhich the frame metadata is added, and is data of which real timeperformance is required at a time of reproduction of a video signal andthe like (real time metadata). That is, the frame metadata for exampleincludes an LTC as a time code for distinguishing a video signalcorresponding to the frame by predetermined time information such as adate and time (year, month, day, hour, minute, and second), a user bit(UB) indicating a signal characteristic of the video signal of theframe, a UMID, GPS (Global Positioning System) information indicating aposition where image pickup by the video camera was performed, anessence mark as information on contents of essence data such as thevideo signal, audio signal and the like, ARIB (Association of RadioIndustries and Businesses) metadata, and setting/control information ofthe video camera that performed the image pickup.

[0067] The ARIB metadata is standardized by the ARIB, and issuperimposed on a standard communication interface such as SDI (SerialDigital Interface) or the like. The setting/control information of thevideo camera is for example an IRIS control value, a white balance/blackbalance mode, lens information on a zoom, focus and the like of thelens, and the like.

[0068] The frame meta annual ring data 84 thus includes a real time andan LTC 85 as frame time information using a time independent from thereal time referring to a predetermined time. The LTC 85 is a set of LTCsadded to respective frames. The LTC 85 includes LTCs corresponding toall the frames of the video annual ring data 82 included in the sameannual ring data 80. At a time of reproduction of the audio annual ringdata 81 and the video annual ring data 82, the LTC 85 is reproducedtogether with the audio annual ring data 81 and the video annual ringdata 82.

[0069] Data is recorded on the optical disk 17 in a form of a spiral ora concentric circle from an inner circumference side to an outercircumference side of the optical disk 17. Thus, annual ring data 80including audio data 81 and image data 82 corresponding to the samereproduction time, and low resolution data 83 and frame metadata 84corresponding to the audio data 81 and the image data 82 is recorded onthe optical disk 17 in order in which the data is obtained by imagepickup, whereby the pieces of data corresponding to each other arerecorded (arranged) at positions physically adjacent to each other onthe optical disk 17. The optical disk 17 thus makes it possible toreduce seek time and reduce processing time and a load necessary inprocessing at a time of data reproduction (at a time of readingprocessing).

[0070] Following a plurality of pieces of annual ring data 80 thusrecorded for one clip, clip metadata 91 is recorded.

[0071] The clip metadata 91 corresponds to the whole of the added clip,and is data of which real time performance is not required at a time ofreproduction of a video signal or the like (hereinafter referred to alsoas non-real time metadata). The clip metadata for example includes aconversion table 92 for associating an LTC corresponding to each framewith a frame number, a UMID, GPS information, and other information. Theclip metadata 91 is mainly used at a time of editing audio data andimage data or at a time of search, for example. The clip metadata 91therefore includes data of types not required at a time of reproductionof image data and the like.

[0072] Incidentally, the frame metadata and the clip metadata mayinclude data other than that described above. Also, the frame metadataand the clip metadata may include data of the same contents, theabove-described pieces of data as the frame metadata may be used as theclip metadata, or conversely the above-described pieces of data as theclip metadata may be used as the frame metadata.

[0073] For example, the essence mark, the ARIB metadata, thesetting/control information of the video camera, or the like may be usedas clip metadata, or may be included in both the frame metadata and theclip metadata. Also, the UMID, the GPS information or the like may beincluded in the frame metadata, or may be included in both the framemetadata and the clip metadata.

[0074] The conversion table 92 included in the clip metadata 91 in FIG.3A is a table corresponding to LTCs included in annual ring dataextending from first annual ring data, or annual ring data recorded nextto clip metadata recorded immediately preceding the clip metadata 91, toannual ring data recorded immediately before the clip metadata 91. Theconversion table 92 is therefore recorded somewhat close (as comparedwith a case of FIG. 3B to be described later) to the audio annual ringdata 81 and the video annual ring data 82 to which the conversion table92 corresponds.

[0075] Basically real time performance is not required of metadataincluded in the clip metadata 91. However, when a user uses theconversion table 92 to give an instruction for reproduction of aspecific frame, for example, it is preferable that the audio annual ringdata 81 and the video annual ring data 82 to be reproduced be recordedclose to the conversion table 92, because it can reduce seek time andincrease speed at which the audio annual ring data 81 and the videoannual ring data 82 are read.

[0076] Incidentally, clip metadata may be recorded together in an areadifferent from an area for storing annual ring data, as shown in FIG.3B, for example. In the case of FIG. 3B, clip metadata such as clipmetadata 111-1, clip metadata 111-2, and clip metadata 111-3 is recordedtogether in an area different from an area for recording annual ringdata such as annual ring data 100-1 including audio annual ring data101-1, video annual ring data 102-1, low resolution annual ring data103-1, and frame meta annual ring data 104-1, and annual ring data 100-2including audio annual ring data 101-2, video annual ring data 102-2,low resolution annual ring data 103-2, and frame meta annual ring data104-2.

[0077] Each of the pieces of clip metadata 111-1 to 111-3 includes oneof conversion tables 92-1 to 92-3. These conversion tables 112-1 to112-3 have registered therein a start point, a change point, and an endpoint (that is, a frame at which an LTC value is discontinuous with anLTC value of an immediately preceding frame (or an immediatelysucceeding frame)) of LTC included in corresponding frame meta annualring data.

[0078] It is to be noted that the conversion tables 112-1 to 112-3 arenot limited to this, and LTC may be registered at predeterminedintervals, for example. The larger the number of LTCs registered in aconversion table is, the more the time for calculating a frame number ofa requested frame can be reduced at a time of frame retrieval. However,increase in data size of the conversion table may lengthen a totalretrieval processing time. It is therefore desirable to select LTCs usedfor the conversion tables such that the conversion tables are ofappropriate size.

[0079] In this case, the clip metadata is recorded in the area differentfrom that of the annual ring data after an audio data recording task, aimage data recording task, a low resolution data recording task, and aframe metadata recording task are finished.

[0080] Thus, the conversion tables 112-1 to 112-3 included in the clipmetadata 111-1 to 111-3, respectively, are recorded in proximity to eachother. Hence, when a specific frame is retrieved using the plurality ofconversion tables, seek time can be reduced and the target frame can beretrieved quickly.

[0081] In addition, when the audio data and the image data arereproduced, since the clip metadata unnecessary for the reproduction isnot present between these pieces of data, it is possible to reducereading time and increase speed of reproduction processing.

[0082] Further, the clip metadata includes metadata of which real timeperformance is not required, and normally the clip metadata does notrequire seek time to be taken into consideration. Therefore the clipmetadata may be disposed at any physical position in a storage area ofthe optical disk 17; for example, one piece of clip metadata may berecorded in a distributed manner at a plurality of positions.

[0083] As described above, LTC is recorded as frame metadata togetherwith essence data such as image data, audio data and the like, andconversion tables including a start point, a change point, and an endpoint of the LTC and the like are recorded as clip metadata. Thus, whenediting data recorded on the optical disk 17 described above, a user canperform edit processing easily on the basis of the LTC, and alsoretrieve and reproduce a target frame on the basis of the LTC.

[0084] Description will next be made of a file system for managing thedata recorded on the optical disk 17, and a directory structure andfiles in the file system.

[0085] Any file system may be used as the file system for managing thedata recorded on the optical disk 17. For example, UDF (Universal DiskFormat), ISO 9660 (International Organization for Standardization 9660)or the like may be used. When a magnetic disk such as a hard disk isused in place of the optical disk 17, FAT (File Allocation Tables), NTFS(New Technology File System), HFS (Hierarchical File System), UFS (Unix(registered trademark) File System) or the like may be used as the filesystem. Alternatively, a special file system may be used.

[0086] In this file system, the data recorded on the optical disk 17 ismanaged by a directory structure and files as shown in FIG. 4.

[0087] A root directory (ROOT) 131 in FIG. 4 has a PROAV directory 132including subdirectories in which information on essence data such asimage data, audio data and the like, edit lists representing results ofediting the essence data, and the like are disposed. Though not shown,constructing table data and the like are disposed in the root directory131.

[0088] The PROAV directory 132 includes: a disk metafile (DISCMETA.XML)133 as a file including information such for example as a title andcomments for all the essence data recorded on the optical disk 17 and apath to image data corresponding to a representative picture as a framerepresentative of all the image data recorded on the optical disk 17;and an index file (INDEX.XML) 134 and an index file (INDEX.RSV) 135including for example managing information for managing all clips andedit lists recorded on the optical disk 17. Incidentally, the index file135 is a reproduction of the index file 134. The two files are providedto improve reliability.

[0089] The PROAV directory 132 includes a disk information file(DISCINFO.XML) 136 and a disk information file (DISCINFO.RSV) 137, whichare metadata for the entire data recorded on the optical disk 17 and afile including information such as disk attributes, a reproduction startposition, or Reclnhi, for example. Incidentally, the disk informationfile 137 is a reproduction of the disk information file 136. The twofiles are provided to improve reliability. However, when the informationis updated, only the disk information file 136 may be updated.

[0090] In addition to the files described above, the PROAV directory 132further includes a clip root directory (CLPR) 138 having clip datadisposed in subdirectories and an edit list root directory (EDTR) 139having edit list data disposed in subdirectories.

[0091] In the clip root directory 138, the clip data recorded on theoptical disk 17 is managed in different, separate directories one foreach clip. In the case of FIG. 4, for example, three pieces of clip dataare managed in three separate directories, that is, a clip directory(C001) 141, a clip directory (C0002) 142, and a clip directory (C0003)143.

[0092] Specifically, data of a first clip recorded on the optical disk17 is managed as files in a subdirectory of the clip directory 141; dataof a second clip recorded on the optical disk 17 is managed as files ina subdirectory of the clip directory 142; and data of a third cliprecorded on the optical disk 17 is managed as files in a subdirectory ofthe clip directory 143.

[0093] In the edit list root directory 139, the edit lists recorded onthe optical disk 17 are managed in different, separate directories onefor each edit process. In the case of FIG. 4, for example, four editlists are managed in four separate directories, that is, an edit listdirectory (EO001) 144, an edit list directory (E0002) 145, an edit listdirectory (E0003) 146, and an edit list directory (E0004) 147.

[0094] Specifically, the edit list representing a result of firstediting of the clips recorded on the optical disk 17 is managed as filesin a subdirectory of the edit list directory 144; the edit listrepresenting a result of second editing is managed as files in asubdirectory of the edit list directory 145; the edit list representinga result of third editing is managed as files in a subdirectory of theedit list directory 146; and the edit list representing a result offourth editing is managed as files in a subdirectory of the edit listdirectory 147.

[0095] In the subdirectory of the clip directory 141 provided in theabove-described clip root directory 138, the data of the first cliprecorded on the optical disk 17 is provided and managed as files asshown in FIG. 5.

[0096] In the case of FIG. 5, the clip directory 141 includes: a clipinformation file (CO001C01.SMI) 151 for managing this clip; a image datafile (C0001V01.MXF) 152 including image data of the clip; eight audiodata files (C0001A01.MXF to C0001A08.MXF) 153 to 160 including audiodata of channels of the clip; a low resolution data file (C0001SO1.MXF)161 including low resolution data corresponding to the image data of theclip; and a clip metadata file (C0001M01.XML) 162 corresponding to theessence data of the clip and including clip metadata, which is metadatasuch as a conversion table for associating LTC with frame numbers, forexample, of which metadata real time performance is not required.

[0097] The clip directory 141 further includes: a frame metadata file(C0001R01.BIM) 163 corresponding to the essence data of the clip andincluding frame metadata, which is metadata such as the LTC, forexample, of which metadata the real time capability is required; and apicture pointer file (C0001101.PPF) 164 for describing frame structureof the image data file 152 (for example information on a compressionform of each picture in MPEG or the like, and information on an offsetaddress from a start of the file and the like).

[0098] In the case of FIG. 5, the image data, the low resolution data,and the frame metadata, of which data the real time capability isrequired at a time of reproduction, are each managed as one file so asnot to increase reading time.

[0099] While the real time capability is required also of the audio dataat a time of reproduction, eight channels are provided to supportmultiple audio channels such as 7.1 channels or the like, and aremanaged as different files, respectively. That is, the audio data ismanaged as eight files in the above description; however, the presentinvention is not limited to this, and a number of files corresponding tothe audio data may be 7 or less, or 9 or more.

[0100] Similarly, the image data, the low resolution data, and the framemetadata may be each managed as two or more files in some cases.

[0101] In FIG. 5, the clip metadata of which the real time capability isnot required is managed as a file different from that of the framemetadata of which the real time capability is required. This is toprevent reading of the metadata that is not required during normalreproduction of the image data and the like. It is thereby possible toreduce processing time of reproduction processing and a load necessaryin the processing.

[0102] Incidentally, while the clip metadata file 162 is described in anXML (extensible Markup Language) format for versatility, the framemetadata file 163 is in a BiM format in which the data described by XMLis encoded in a binary format, in order to reduce the processing time ofthe reproduction processing and the load necessary in the processing.

[0103] Incidentally, the BiM encoded in the binary format, such as theframe metadata file (C0001R01.BIM) 163, will be described later withreference to FIG. 7 and subsequent figures.

[0104] The example of structure of the files in the clip directory 141shown in FIG. 5 is applicable in all clip directories corresponding toeach clip recorded on the optical disk 17. Specifically, the example ofstructure of the files shown in FIG. 5 is applicable in the other clipdirectories 142 and 143 shown in FIG. 4. Therefore description of theclip directories 142 and 143 will be omitted.

[0105] While the files included in a clip directory corresponding to oneclip have been described above, the structure of the files is notlimited to the above example, and may be any structure as long as a clipmetadata file corresponding to the clip is present in a subdirectory ofthe clip directory.

[0106] Description will next be made of an example of structure of filesin a subdirectory of the edit list root directory 139 in FIG. 4. In thesubdirectory of the edit list directory 145 provided in theabove-described edit list root directory 139, edit list data asinformation on the result of the second editing of the clip datarecorded on the optical disk 17 is provided and managed as files asshown in FIG. 6.

[0107] In the case of FIG. 6, the edit list directory 145 includes: anedit list file (E0002E01.SMI) 171 for managing this edit result (editlist); an edit list clip metadata file (E0002M01.XML) 172 including clipmetadata corresponding to essence data after this edit (parts extractedas data after the edit from the essence data of all clips used in theedit), or clip metadata newly generated on the basis of the clipmetadata; a play list file (E0002P01.SMI) 173 including information suchfor example as a reproduction procedure (play list) of the essence dataon the basis of this edit result (edit list); and a play list picturepointer file (E0002101.PPF) 174 for describing frame structure of imagedata reproduced on the basis of the reproduction procedure included inthe play list file 173 (for example information on a compression form ofeach picture in MPEG or the like, and information on an offset addressfrom a start of the file and the like).

[0108] The edit list directory 145 further includes: a play list imagedata file (E0002V01.BMX) 175 including image data for-ensuring real timereproduction based on the reproduction procedure (play list) of the playlist file 173; four play list audio data files (E0002A01.BMX toE0002A04.BMX) 176 to 179 including audio data for ensuring real timereproduction based on the reproduction procedure (play list) of the playlist file 173; a play list low resolution data file (E0002S01.BMX) 180including low resolution data for ensuring real time reproduction basedon the reproduction procedure (play list) of the play list file 173; anda play list frame metadata file (E0002R01.BBM) 181 including framemetadata for ensuring real time reproduction based on the reproductionprocedure (play list) of the play list file 173.

[0109] In FIG. 6, the clip metadata of which the real time capability isnot required is managed as a file different from that of the framemetadata of which the real time capability is required. This is toprevent reading of the metadata that is not required during reproductionof the image data and the like using the reproduction procedure (playlist) (during reproduction of the edit result). It is thereby possibleto reduce processing time of reproduction processing and a loadnecessary in the processing.

[0110] The edit list clip metadata file 172 includes new clip metadatagenerated on the basis of clip metadata (clip metadata files present inthe subdirectories of the clip root directory 138) of the clips used inthe edit and on the basis of the edit result. For example, when the editis performed, parts corresponding to the essence data after the edit areextracted from the clip metadata included in the clip metadata file 162in FIG. 5, and these parts are used to reconstruct new clip metadatawith the essence data after the edit as one clip and manage the clipmetadata as the edit list clip metadata file.

[0111] That is, the new clip metadata for the essence data after theedit as one clip is added to the essence data after the edit. The clipmetadata is managed as one edit list clip metadata file. Thus, the editlist clip metadata file is generated for each edit.

[0112] Incidentally, the edit list clip metadata file 172 is describedin the XML format for versatility.

[0113] The image data included in the play list image data file 175, theaudio data included in the play list audio data files 176 to 179, thelow resolution data included in the play list low resolution data file180, and the frame metadata included in the play list frame metadatafile 181 are extracted from the image data, the audio data, the lowresolution data, and the frame metadata, respectively, corresponding tothe clips managed in the subdirectories of the clip root directory 138in FIG. 5, and correspond to the edit result.

[0114] These pieces of data are read when reproduction processing isperformed on the basis of the reproduction procedure (play list)included in the play list file 173. The provision of the pieces of datacorresponding to the edit result makes it possible to reduce a number offiles to be read in reproduction processing based on the play list andreduce time of the processing and a load necessary in the processing.

[0115] Incidentally, each of the image data, the low resolution data,and the frame metadata may be managed as a plurality of files in somecases. Also, a number of files corresponding to the audio data may bethree or less, or five or more.

[0116] The play list frame metadata file 181 is in a BBM formatcorresponding to the BIM format obtained by compiling a file in the XMLformat in order to reduce the processing time of reproduction processingand a load necessary in the processing.

[0117] The example of structure of the files in the edit list directory145 shown in FIG. 6 is applicable in all the edit lists (edit results).Specifically, the example of structure of the files shown in FIG. 6 isapplicable in the other edit list directory 144, 146, or 147 shown inFIG. 4. Therefore description of the edit list directories 144, 146, and147 will be omitted.

[0118] While the files included in an edit list directory correspondingto one editing operation have been described above, the structure of thefiles is not limited to the above example, and may be any structure aslong as an edit list clip metadata file corresponding to the editing ispresent in a subdirectory of the edit list directory.

[0119] Description will next be made of data included in clip metadata.As described above, the clip metadata includes a conversion table of LTCand frame numbers, a UMID, GPS information, and other information. Thesepieces of information are standardized information that may be stored inframe metadata, and are KLV (Key Length Value)-encoded data (hereinafterreferred to as KLV data) including key data, length data, and value datain order to ensure communication of a synchronizing system using astandard interface such as an SDI (Serial Digital Interface) or the likebecause real time performance may be required. This format complies withSMPTE 336M.

[0120] The key data of the KLV data is an identifier indicating aKLV-encoded data item. Identifiers corresponding to various data itemsdefined in an SMPTE metadata dictionary are used as the identifier. Thelength data of the KLV data indicates length of the value data in bytes.The value data of the KLV data includes data proper such as text data asin XML documents or the like. That is, the KLV data is obtained byencoding the data of the data item indicated by the key data, the dataof the data length indicated by the length data, and the datarepresented by the value data.

[0121] Thus, the conversion table and the UMID are actually part of theKLV data; however, for simplicity of description, metadata (KLV data)other than the conversion table and the UMID included in the clipmetadata will be referred to as KLV data.

[0122] It is to be noted that the above-described encoding method is anexample, and that each piece of information included in the clipmetadata may be encoded by a method other than the KLV encoding method,or may be uncoded.

[0123] Description will next be made of a BiM compression-coded in abinary format, such as the frame metadata file (C0001R01.BIM) 163 shownin FIG. 5. A BiM encoder is required to compression-code metadatadescribed by XML and thereby generate a BiM, while a BiM decoder isrequired to decode the BiM and interpret contents thereof. The editingterminal apparatus 16 has a BiM encoder and a BiM decoder included inthe clip data editing unit 54.

[0124] The BiM encoder has a schema definition document in which asystem for describing metadata as a source of a BiM is defined. The BiMdecoder also has the schema definition document in which the system fordescribing the metadata as the source of the BiM is defined. When theBiM encoder and the BiM decoder have the common schema definitiondocument, the BiM decoder can completely interpret the BiM generated bythe BiM encoder. In other words, when the BiM encoder generates a BiM onthe basis of a non-standard, original schema definition document and theBiM decoder has only a standard schema definition document, the BiMdecoder can interpret only a standard part included in the BiM.

[0125]FIG. 7 shows an example of standard real time metadata describedby XML before being encoded into a BiM by the BiM encoder. This standardreal time metadata includes: a Wrapper including a standard name spaceidentifier as a Root (“urn:schemas-proDisc:realTimeMeta” in thisexample) (first row), a UMID (second row), and a Filler for ECCalignment (third row); and a description corresponding to each frame.The description corresponding to each frame includes: essential itemsincluding a Bitfiller (fifth row) for byte alignment, an LTC (sixthrow), a UMID (seventh row), and a KLV (eighth row); and a Filler (ninthrow) for adjusting length of a fragment update unit (FUU) in the BiM.

[0126] The standard real time metadata before being encoded into the BiMis characterized by being provided with the Fillers for ECC alignment,byte alignment, and FUU length adjustment. The standard real timemetadata is characterized especially in that the Bitfiller for bytealignment of a boundary of the essential items including the LTC, theUMID, and the KLV is provided in the encoded BiM.

[0127] Next, FIG. 8 shows an example of non-standard real time metadatadescribed by XML before being encoded into a BiM by the BiM encoder,that is, extended real time metadata including original items (forexample video camera setting/control information, ARIB metadata and thelike) (hereinafter referred to as original items) added by amanufacturer in addition to standard items. This non-standard real timemetadata includes: a Wrapper including a non-standard name spaceidentifier as a Root (“urn:schemas-proDisc:realTimeMeta:cameraMeta” inthis case) (first row), a UMID (second row), and a Filler for ECCalignment (third row); and a description corresponding to each frame.

[0128] The description corresponding to each frame includes: essentialitems including a Bitfiller (fifth row) for byte alignment correspondingto each frame, an LTC (sixth row), a UMID (seventh row), and a KLV(eighth row); original items (ninth to 17th rows) including video camerasetting/control information; and a Filler (19th row) for adjustinglength of a fragment update unit (FUU) in the BiM.

[0129] The non-standard real time metadata before being encoded into theBiM is also characterized by being provided with the Fillers for ECCalignment, byte alignment, and FUU length adjustment. The non-standardreal time metadata is characterized especially in that the Bitfiller forbyte alignment of a boundary of the essential items including the LTC,the UMID, and the KLV is provided in the encoded BiM.

[0130] Incidentally, non-standard real time metadata describing ARIBmetadata or the like as an original item is also described in the samemanner as in FIG. 8.

[0131] Processing for generating the BiM of standard real time metadataas shown in FIG. 7 will next be described with reference to a flowchartof FIG. 9. In step S1, the clip data editing unit 54 describes in aWrapper a name space identifier (“urn:schemas-proDisc:realTimeMeta” inthis example) defined in a standard schema. In step S2, the clip dataediting unit 54 describes a UMID and a Filler for ECC alignment. In stepS3, the clip data editing unit 54 describes a Bitfiller for bytealignment at a start of data corresponding to each frame, and thendescribes essential items including an LTC, a UMID, and a KLV. In stepS4, the clip data editing unit 54 adds, at an end of the essentialitems, a Filler for adjusting length of a fragment update unit in theBiM, and thereby describes standard real time metadata. In step S5, theclip data editing unit 54 compression-codes the standard real timemetadata in a binary format by the BiM encoder included in the clip dataediting unit 54, and thereby generates a standard BiM.

[0132] Processing for generating the BiM of non-standard real timemetadata as shown in FIG. 8 will next be described with reference to aflowchart of FIG. 10. In step S11, the clip data editing unit 54describes in a Wrapper a name space identifier(“urn:schemas-proDisc:realTimeMeta:cameraMeta” in this example) definedin advance in a non-standard, original schema of a manufacturer. In stepS12, the clip data editing unit 54 describes a UMID and a Filler for ECCalignment. In step S13, the clip data editing unit 54 describes aBitfiller for byte alignment at a start of data corresponding to eachframe, and then describes essential items including an LTC, a UMID, anda KLV. In step S14, the clip data editing unit 54 describes originalitems (video camera setting/control information in this case). In stepS15, the clip data editing unit 54 adds, at an end of the essentialitems, a Filler for adjusting length of a fragment update unit in theBiM, and thereby describes non-standard real time metadata. In step S16,the clip data editing unit 54 compression-codes the non-standard realtime metadata in a binary format by the BiM encoder included in the clipdata editing unit 54, and thereby generates a non-standard BiM.

[0133] As described above, when real time metadata is encoded in abinary format and thereby a BiM is generated, byte alignment isperformed at a boundary of essential items including an LTC, a UMID, anda KLV in the BiM. It is therefore possible to quickly find a positionwhere the essential items are described when reading the thus formedBiM. It is thus possible to reduce time required to read the BiM andreduce an amount of resources to be used as compared with a case wherebyte alignment is not performed at the boundary of the essential items.

[0134] Incidentally, while the method of first describing real timemetadata using XML and then converting the real time metadata to abinary format using the BiM encoder has been described above, thedescription using XML may be omitted to output BiM data directly byobtaining a binary format based on a schema in advance.

[0135] Description will next be made of processing for reading a BiM ofreal time metadata simultaneously with reproduction of clip data, forexample. In step S21, the clip data editing unit 54 reads a name spaceidentifier described in a Wrapper of the BiM using the BiM decoderincluded in the clip data editing unit 54. In step S22, the clip dataediting unit 54 determines whether or not the read name space identifieris defined in a schema possessed by the clip data editing unit 54. Whenthe clip data editing unit 54 determines that the read name spaceidentifier is defined in the schema possessed by the clip data editingunit 54, the processing proceeds to step S23.

[0136] In step S23, the clip data editing unit 54 recognizes essentialitems included in the BiM as valid data. Further, in step S24, the clipdata editing unit 54 recognizes original items included in the BiM asvalid data. In step S25, the clip data editing unit 54 removes a Fillerfrom the BiM, and thereafter uses the data recognized as valid (data ofthe essential items and the original items in this case) for editprocessing and the like. Thereby the data recognized as valid isdisplayed on a screen, for example.

[0137] On the other hand, when the read name space identifier is forexample “urn:schemas-proDisc:realTimeMeta:cameraMeta” and the schemapossessed by the clip data editing unit 54 is a standard schema, theclip data editing unit 54 determines in step S22 that the read namespace identifier is not defined in the schema possessed by the clip dataediting unit 54, and then the processing proceeds to step S26.

[0138] In step S26, the clip data editing unit 54 recognizes theessential items included in the BiM as valid data. In step S27, the clipdata editing unit 54 recognizes the original items as invalid data, thatis, data unrecognizable by the clip data editing unit 54 (specifically,the clip data editing unit 54 recognizes the original items as a Fillerhaving no substantial meaning). In step S25, the clip data editing unit54 removes a Filler from the BiM, and thereafter uses the datarecognized as valid (only data of the essential items in this case) foredit processing and the like. Thereby only the data recognized as validis displayed on the screen, for example. At this time, the data of theoriginal items is recognized as invalid data (that is, a Filler) and isthus not displayed on the screen. In this case, presence of the data ofthe original items of a manufacturer is not recognized by apparatus madeby other manufacturers. It is therefore possible to enhance secrecy ofthe original items and prevent analysis and the like of the data of theoriginal items.

[0139] Conversely, however, a certain character string (for example astring of zeros) may be displayed to make known the presence of the dataof the original items recognized as invalid.

[0140] Incidentally, when real time metadata not encoded into a BiM isread simultaneously with reproduction of clip data, for example, similarprocessing can also be performed to read only data recognizable by theclip data editing unit 54 and not to read data unrecognizable by theclip data editing unit 54. In the present situation, however, real timemetadata not encoded into BiM does not exist.

[0141] Further, while the method of processing real time metadata usinga BiM decoder has been described above, essential items may be readdirectly without using a BiM decoder by designing a schema such that forexample a byte offset of essential items in BiM technical data from aspecified position is fixed regardless of whether or not the schema is astandard schema or a non-standard schema.

[0142] Description will next be made of handling of non-real timemetadata by the clip data editing unit 54. As described above, aconversion table 92, a UMID, GPS information, or other information isdescribed by using XML in clip metadata 91, which is a kind of non-realtime metadata.

[0143] As with the above-described real time metadata, non-real timemetadata can include original data of a manufacturer in addition toessential item data recorded as standard data. It is described in a namespace defined in advance in an original schema of the manufacturer.

[0144] Processing for reading non-real time metadata including originalitems for use in clip data edit processing and the like will next bedescribed with reference to a flowchart of FIG. 12.

[0145] In step S31, the clip data editing unit 54 reads a name spaceidentifier of non-real time metadata. In step S32, the clip data editingunit 54 recognizes essential items described in a standard name spaceand included in the non-real time metadata as valid data.

[0146] In step S33, the clip data editing unit 54 determines whether ornot a non-standard name space (that is, a non-standard name spaceoriginal to a manufacturer) is detected. When the clip data editing unit54 determines that a non-standard name space is detected, the clip dataediting unit 54 determines in step S34 whether or not the detectednon-standard name space is recognizable. When the clip data editing unit54 determines that the detected non-standard name space is recognizable,the processing proceeds to step S35. In step S35, the clip data editingunit 54 recognizes original items described in the non-standard namespace as valid data.

[0147] On the other hand, when the clip data editing unit 54 determinesin step S34 that the detected non-standard name space is notrecognizable, the processing proceeds to step S36. In step S36, the clipdata editing unit 54 recognizes the original items described in thenon-standard name space as invalid data.

[0148] In step S37, the clip data editing unit 54 reads the datarecognized as valid and skips reading the data recognized as invalid.The read data is used for clip data edit processing. The processingthereafter returns to step S32 to repeat processing from step S32 ondown.

[0149] Incidentally, when the clip data editing unit 54 determines instep S33 that a non-standard name space is not detected, processing insteps S34 to S36 is skipped to proceed to step S37.

[0150] As described above, when non-real time metadata is read for apurpose of clip data edit processing, for example, only original itemdata defined in a schema and comprehended by the clip data editing unit54 is read, and original item data of another manufacturer, for example,which data is not defined in the schema is ignored without being read.It is therefore possible to use the read non-real time metadataefficiently.

[0151] Processing for editing non-real time metadata itself includingoriginal items, and then rerecording the non-real time metadata onto theoptical disk 17 or transferring the non-real time metadata to anotherapparatus will next be described with reference to a flowchart of FIG.13.

[0152] In step S41, the clip data editing unit 54 reads a name spaceidentifier for the original items of the non-real time metadata. In stepS42, the clip data editing unit 54 determines whether or not the readname space identifier is defined in a schema possessed by the clip dataediting unit 54. When the clip data editing unit 54 determines that theread name space identifier is defined in the schema possessed by theclip data editing unit 54, the processing proceeds to step S43.

[0153] In step S43, the clip data editing unit 54 recognizes essentialitems included in the non-real time metadata as valid data. Further, instep S44, the clip data editing unit 54 recognizes the original itemsincluded in the non-real time metadata as valid data. In step S45, theclip data editing unit 54 reads the data recognized as valid (data ofboth the essential items and the original items in this case) and datarecognized as invalid. In step S46, the clip data editing unit 54 editsonly the read data recognized as valid as appropriate in such a manneras to correspond to user operation, for example. Incidentally, theprocessing in step S46 may be omitted.

[0154] In step S47, the clip data editing unit 54 rerecords the datarecognized as valid which data is edited as appropriate and the datarecognized as invalid which data is read in step S45 onto the opticaldisk 17 or transfers the data recognized as valid and the datarecognized as invalid to another apparatus without destroying the datarecognized as invalid.

[0155] On the other hand, when the clip data editing unit 54 determinesin step S42 that the read name space identifier is not defined in theschema possessed by the clip data editing unit 54, the processingproceeds to step S48. In step S48, the clip data editing unit 54recognizes the essential items included in the non-real time metadata asvalid data. In step S49, the clip data editing unit 54 recognizes theoriginal items included in the non-real time metadata as invalid data.In step S45, the clip data editing unit 54 reads the data recognized asvalid (data of the essential items in this case) and the data recognizedas invalid (data of the original items in this case). Then, processingafter step S45 is performed in the same manner as described above.

[0156] As described above, when non-real time metadata itself is edited,for example, data of original items of another manufacturer, forexample, not defined in the schema is not edited. When the non-real timemetadata is further rerecorded or transferred, the data of originalitems of the other manufacturer, for example, not defined in the schemais rerecorded or transferred together with data of essential items anddata of original items defined in the schema and thus comprehended. Itis therefore possible to protect even the original item data notcomprehended by the clip data editing unit 54 without deleting orchanging the information.

[0157] It is to be noted that while the above description has been madeof a case where data such as image data, audio data, low resolutiondata, frame metadata, clip metadata, edit lists and the like is recordedon an optical disk, a recording medium for recording these pieces ofdata is not limited to the optical disk. For example, the recordingmedium may be a magnetic disk such as a flexible disk or a hard disk, amagnetic tape, or a semiconductor memory such as a flash memory.

[0158] In addition, while a case where the editing terminal apparatus 16performs editing has been described above, the information processingapparatus for performing the editing is not limited to the editingterminal apparatus 16. For example, the information processing apparatusmay be the planning terminal apparatus 11, the image pickup device 14,or the field PC 15 in FIG. 1, or may be an information processingapparatus other than the above.

[0159] The series of processes described above can be carried out notonly by hardware but also by software as described above. When theseries of processes is to be carried out by software, a programincluding the software is installed from a recording medium or the likeonto a computer incorporated in special hardware, or for example ageneral-purpose personal computer that can execute various functions byinstalling various programs thereon.

[0160] As shown in FIG. 2, the recording medium is not only formed bythe removable medium 71 distributed to users to provide the programseparately from the editing terminal apparatus 16, the removable medium71 including a packaged medium including a magnetic disk (includingflexible disks), an optical disk (including CD-ROMs, DVDs,magneto-optical disks, and MDs), a semiconductor memory or the likewhich has the program recorded thereon, but also formed by the ROM 52,the hard disk including the storage unit 63, or the like which has theprogram stored thereon and is provided to the user in a state of beingpreincorporated in the computer.

[0161] It is to be noted that in the present specification, the stepsdescribing the program provided by the medium include not onlyprocessing carried out in time series in the described order but alsoprocessing carried out in parallel or individually and not necessarilyin time series.

[0162] Also, in the present specification, a system refers to anapparatus as a whole formed by a plurality of apparatus.

What is claimed is:
 1. An information processing apparatus forreproducing metadata including information on material data, saidinformation processing apparatus comprising: determining means fordetermining whether or not said metadata inputted is defined in advance;and reproducing means for reproducing standard item data andnon-standard item data included in said metadata when said determiningmeans determines that said metadata is defined in advance, andreproducing only the standard item data included in said metadata whensaid determining means determines that said metadata is not defined inadvance.
 2. An information processing apparatus as claimed in claim 1,wherein said metadata is described using one of XML (extensible MarkupLanguage) and BiM, which is a binary format of XML.
 3. An informationprocessing apparatus as claimed in claim 1, wherein said determiningmeans determines whether or not said metadata is defined in advance on abasis of whether or not a name space identifier described in saidmetadata is defined in a schema possessed by said information processingapparatus.
 4. An information processing apparatus as claimed in claim 1,wherein said metadata is real time metadata to be read simultaneouslywith reproduction of said material data.
 5. An information processingmethod for reproducing metadata including information on material data,said information processing method comprising: a determining step fordetermining whether or not said metadata inputted is defined in advance;and a reproducing step for reproducing standard item data andnon-standard item data included in said metadata when it is determinedby processing of said determining step that said metadata is defined inadvance, and reproducing only the standard item data included in saidmetadata when it is determined by the processing of said determiningstep that said metadata is not defined in advance.
 6. A program forreproducing metadata including information on material data, saidprogram making a computer execute a process comprising: a determiningstep for determining whether or not said metadata inputted is defined inadvance; and a reproducing step for reproducing standard item data andnon-standard item data included in said metadata when it is determinedby processing of said determining step that said metadata is defined inadvance, and reproducing only the standard item data included in saidmetadata when it is determined by the processing of said determiningstep that said metadata is not defined in advance.
 7. A recording mediumon which a computer readable program for reproducing metadata includinginformation on material data is recorded, said program comprising: adetermining step for determining whether or not said metadata inputtedis defined in advance; and a reproducing step for reproducing standarditem data and non-standard item data included in said metadata when itis determined by processing of said determining step that said metadatais defined in advance, and reproducing only the standard item dataincluded in said metadata when it is determined by the processing ofsaid determining step that said metadata is not defined in advance.